macromedia Your Account International Help
Products Support & Training DevNet Solutions Partners Downloads Store
Products Support & Training DevNet Solutions Partners Downloads Store
Home > Products > Dreamweaver > Support > TechNote Index
Macromedia Dreamweaver Support Center - TechNote

ASP.NET control rendering problems related to .NET installation

Issue
In some situations, after installing the .NET Framework or SDK on a Dreamweaver development machine, built-in ASP.NET controls do not render correctly in Dreamweaver. Controls are rendered as if the Framework is not available.

For example, a simple RadioButtonList, instead of showing the actual list values, appears as follows:

Note: This is the default rendering seen in Dreamweaver when the .NET Framework or SDK is not installed.

Reason
In order for built-in ASP.NET controls to render correctly on a machine with the .NET Framework installed, the computer user's PATH environment variable must include the path to the .NET RegAsm.exe file. In some instances during .NET installation, the PATH environment variable is not updated as expected.

Solution
First, determine the path to RegAsm.exe. The easiest way to identify the path is to search for RegAsm.exe in Windows Explorer. As of .NET version 1.1, it is located in a folder corresponding to the Framework's version number.

The default location for this folder on Windows XP is C:\Windows\Microsoft.NET\ Framework\ v1.1.4322\. After identifying the correct path, check the value of the PATH environment variable, adding the path if needed.

1 Right-click the My Computer icon on the desktop and select Properties.
2 In Properties dialog box select the Advanced tab.
3 On the Advanced tab click the Environment Variables button.
4 Locate PATH in the System Variables section, select it, and click Edit.
5 To see the current value of the PATH variable it's easier to copy the value and paste into Notepad or similar editor. There may be more than one path included in this value.
6 Check that the path to the directory containing RegAsm.exe is part of the path statement.

If the .NET Framework was installed to its default location, the following values are valid.
> .NET Framework version 1.0
> Windows 2000

C:\WINNT\Microsoft.NET\Framework\v1.0.3705 
> Windows XP

C:\Windows\Microsoft.NET\Framework\v1.0.3705
> Win 2000 and XP

%SystemRoot%\Microsoft.NET\Framework\v1.0.3705
> .NET Framework version 1.1
> Windows 2000

C:\WINNT\Microsoft.NET\Framework\v1.1.4322
> Windows XP

C:\Windows\Microsoft.NET\Framework\v1.1.4322
> Win 2000 and XP

%SystemRoot%\Microsoft.NET\Framework\v1.1.4322

Note: .NET version numbers may differ slightly depending on the specific build installed.
7 If the RegAsm.exe path is not found, add it to the path.
 
> Use the path located in the search.
> Add a semicolon to the end of the existing path and add the RegAsm.exe path.
> Do not include RegAsm.exe as part of the path.
> Here is an example PATH for Windows XP. The section in bold is added when performing these steps:

%SystemRoot%;%SystemRoot%\system32; C:\Windows\Microsoft.NET\ Framework\v1.1.4322
8 If editing the Path in a text editor, paste the modified value into the Edit System Variable window and save. Reboot is required.

Additional information
Please read Dreamweaver compatibility issues with the ASP.NET framework version 1.1 (TechNote 18682) for details on a separate issue associated with Dreamweaver that can also cause problems rendering ASP.NET controls in design view.

Developers may also encounter problems if the .NET Framework is installed on the web server prior to IIS installation. In this situation, .NET applications may not be mapped correctly in IIS. ASP.NET pages will not display in a browser, or users will be asked to download or open the file.

For more information, please review the Microsoft Knowledge Base article 325093: ASP.NET Pages Exhibit Unexpected Behavior Because the Server-Side Code Is Not Processed.



ID: 18717
Product: Dreamweaver
Versions: MX, 6.1
OS: Windows 2000, Windows XP
Browser: All
Server: MS IIS or Peer Web Server
Database: All
Former ID:  
How useful was this document?
less more

1

2

3

4

5

How can the document be improved? (300 characters or less - you will not receive a reply.)

Last updated: June 18, 2003
Created: June 23, 2003